3. Creating Domains, Repositories, Data Sources

3.1 Creating Schemas using Repository Creation Utility

1. Open command prompt on Unix and browse to <WL_HOME>/oracle_common/bin and run ./rcu. The following window is displayed.

   

2. Click ‘Next’. The following window is displayed.

   

3. Select ‘Create Repository’ and select ‘System Load and Product Load’. Click ‘Next’. The following screen is displayed.

   

4. Provide database details where you want to create schemas, as shown in the above screen.

Note

You will require a user with SYSDBA role to create schemas.

5. Click ‘Next’. The following window is displayed.

   

6. Click ‘OK’ in the confirmation dialog.
7. Click ‘Next’ the following window is displayed.

   

8. Select ‘Create new Prefix’ option and specify the value. For example, OLL.
9. Select the options ‘Metadata Services’ and ‘Oracle Platform Security Services’ as shown in the above screen. Click ‘Next’. The following window is displayed.

   

10. Click ‘Next’. The following window is displayed.

    

11. You can select one of the following:

• Select ‘Use same password for all schemas’ and specify the password.
• Select ‘Specify different passwords for all schemas’ and specify Schema Passwords for each schema.

12. Click ‘Next’. The following window is displayed.

    

13. Click ‘Next’. The following window is displayed.

    

14. Click ‘OK’ in the confirmation dialog. The following window is displayed.

    

15. Click ‘OK’ in the confirmation dialog. The following window is displayed.

    

16. Click ‘Create’. The following windows are displayed.

    

    

17. Click ‘Close’ to close the window.

3.2 Creating Domain and Servers

1. In Unix/Linux machine, once the Oracle WebLogic Server is installed, navigate to the following path - <WL_HOME>/oracle_common/common/bin.
2. In Unix, run ‘config.sh’

   

3. Select ‘Create a new domain’ and specify the Domain Location.
4. Click ‘Next’ to continue. The following window is displayed.

   

5. Select the option ‘Create Domain Using Product Templates’ in the list of available templates and select ‘Oracle Enterprise Manager [em]’. On selection, the following options are auto-selected:

• Oracle JRF [oracle_common]
• Weblogic coherence cluster Extension [wlserver]

6. Click ‘Next’. The following window is displayed.

   

7. Specify the Domain Name in the ‘Application location’ field. You can click browse to directly select the path (if required). Click ‘Next’. The following window is displayed.

   

8. Enter credentials for the following:

• Name
• Password
• Confirm Password

9. Click ‘Next’. The following window is displayed.

   

10. Select the Domain Mode as ‘Production’ and ‘JDK’ from Available JDKs. You can also select any other JDK by selecting ‘Other JDK Location’ option. Click ‘Next’. The following window is displayed.

    

11. Specify the RCU data and click on ‘Get RCU Configuration’. The following window is displayed.

    

12. Click ‘Next’. The following window is displayed.

    

13. Click ‘Next’. The following window is displayed.

    

14. Select ‘Administration Server’ and ‘Topology’ and click ‘Next’. The following window is displayed.

    

15. Enter Administration ‘Server Name’ and ‘Listen Port’ details. Click ‘Next’. The following window is displayed.

    

16. Click ‘Add’ button to create ‘ManagedServer’.
17. Select the Server Group as ‘JRF-MAN-SVR’. Selecting this server group ensures that the Oracle JRF services are targeted to the specific Managed Servers created.

Note

It is recommended to create two managed servers, one each for UI and Web Services.

18. Click ‘Next’. The following window is displayed.

    

19. Configure as required and click ‘Next’. The following window is displayed.

    

20. Configure as required and click ‘Next’. The following window is displayed.

    

21. Configure as required and click ‘Next’. The following window is displayed.

    

22. Click ‘Create’. The following window is displayed.

    

23. Click ‘Next’. The following window is displayed.

    

24. Click ‘Next’. The following window is displayed.

    

25. Click ‘Next’. The following window is displayed.

    

26. Click ‘Next’. The following window is displayed.

    

27. Once the creation of the Domain is complete, click ‘Finish’ to close the window.

Note

The default Weblogic installation will be running JVM with 512MB, this has to be increased for the ADF managed server. Say, for a 2 CPU Quad Core with 16 GB it could have the JVM running at 8 GB as:

USER_MEM_ARGS="-Xms8192m –Xmx8192m -XX:PermSize=2048m -XX:Max­PermSize=2048m"

28. The "$MW_HOME/user_projects/domains/<mydomain>" directory contains a script that can be used to start the Admin server.

• $ cd $MW_HOME/user_projects/domains/<mydomain>/bin
• $ ./startWebLogic.sh

If the server is required to be running and access to command line needs to be returned use "nohup" and "&"

$ nohup ./startWebLogic.sh &

29. To Start Managed Server

• $ cd $MW_HOME/user_projects/domains/<mydomain>/bin
• $ ./$MW_HOME/user_projects/domains/<mydomain>/bin/startManagedWebLogic.sh {ManagedServer_name} {AdminServer URL}

If the server is required to be running and access to command line needs to be returned use "nohup" and "&".

$ nohup ./$MW_HOME/user_projects/domains/<mydomain>/bin/startManagedWebLogic.sh {ManagedServer_name} {AdminServer URL} &

The recommended parameters for each Managed Server for application and web services are as follows:

• For managed server where application is deployed:

-Xms8g -Xmx8g -XX:NewRatio=3 -XX:HeapDumpPath=/tmp -Dweblogic.threadpool.MinPoolSize=40 -Dweblogic.threadpool.MaxPoolSize=150 -XX:SoftRefLRUPolicyMSPerMB=10 -Dweblogic.diagnostics.debug.DebugLogger.DISABLED=true -Dweblogic.management.discover=false -Dweblogic.llr.table.specjdsl=wl_llr_jent31_1 -Dweblogic.llr.table.specjds2=wl_llr_jent31_2 -Dsun.net.inetaddr.ttl=0 -Dnetworkaddress.cache.ttl=0 -XX:AllocatePrefetchDistance=256 -XX:AllocatePrefetchStyle=1 -XX:+AggressiveOpts -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:MaxTenuringThreshold=4 -XX:-UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=60 -XX:CMSTriggerRatio=60 -XX:+CMSParallelRemarkEnabled -XX:+UseCMSCompactAtFullCollection -XX:+CMSCompactWhenClearAllSoftRefs -XX:PrintCMSStatistics=1 -XX:+PrintClassHistogram -XX:-UseParallelGC -XX:ParallelGCThreads=10 -XX:-TraceClassUnloading -XX:-UseParallelOldGC -XX:+UseCompressedOops -XX:+UseBiasedLocking -XX:+AlwaysPreTouch -XX:-UseAdaptiveSizePolicy -Djbo.load.components.lazily=true -Djbo.ampool.initpoolsize=100 -Djbo.recyclethreshold=200 -Djbo.ampool.minavailablesize=200 -Djbo.ampool.maxavailablesize=200 -Djbo.ampool.timetolive=-1 -Djbo.locking.mode=optimistic -Djbo.doconnectionpooling=true -Djbo.txn.disconnect_level=1 -Djbo.ampool.doampooling=true -Djbo.dofailover=false -Djbo.ampool.maxinactiveage=3600000 -Djbo.ampool.monitorsleepinterval=360000 -Doracle.multitenant.enabled=false -Dweblogic.mdb.message.MinimizeAQSessions=true -Dweblogic.ejb.container.MDBDestinationPollIntervalMillis=6000 -XX:StringTableSize=100003 -XX:ReservedCodeCacheSize=1g -XX:+UseStringCache -XX:+OptimizeStringConcat -XX:+UnlockCommercialFeatures -XX:+FlightRecorder -Doracle.adfm.useSharedTransactionForFrame=false

• For managed server where web services are deployed:

-Xms8g -Xmx8g -XX:NewRatio=3 -XX:HeapDumpPath=/tmp -Dweblogic.threadpool.MinPoolSize=40 -Dweblogic.threadpool.MaxPoolSize=150 -XX:SoftRefLRUPolicyMSPerMB=10 -Dweblogic.diagnostics.debug.DebugLogger.DISABLED=true -Dweblogic.management.discover=false -Dweblogic.llr.table.specjdsl=wl_llr_jent31_1 -Dweblogic.llr.table.specjds2=wl_llr_jent31_2 -Dsun.net.inetaddr.ttl=0 -Dnetworkaddress.cache.ttl=0 -XX:AllocatePrefetchDistance=256 -XX:AllocatePrefetchStyle=1 -XX:+AggressiveOpts -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:MaxTenuringThreshold=4 -XX:-UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=60 -XX:CMSTriggerRatio=60 -XX:+CMSParallelRemarkEnabled -XX:+UseCMSCompactAtFullCollection -XX:+CMSCompactWhenClearAllSoftRefs -XX:-UseParallelGC -XX:ParallelGCThreads=10 -XX:-TraceClassUnloading -XX:-UseParallelOldGC -XX:+UseCompressedOops -XX:+UseBiasedLocking -XX:+AlwaysPreTouch -XX:-UseAdaptiveSizePolicy -Doracle.multitenant.enabled=false -XX:StringTableSize=100003 -XX:ReservedCodeCacheSize=1g -XX:+UseStringCache -XX:+OptimizeStringConcat -XX:+UnlockCommercialFeatures -XX:+FlightRecorder

3.3 Creating Metadata Repository

Assuming that OLL_MDS schema is created using Oracle Repository Creation Utility (RCU) as mentioned in Creating Schemas using Repository Creation Utility section, follow the below steps to create the repository.

1. Login to Oracle Enterprise Manager 12c console (http://hostname:port/em).

   

2. Click on domain name OFSLLREL_domain on the left side panel.
3. Expand Weblogic domain OFSLLREL_domain and click ‘Metadata Repositories’ option, as shown in the above screen.
4. The following window is displayed.

   

5. Click Register button. The following window is displayed.

   

6. Enter database instance details under Database Connection Information section and click ‘Query’. All available schemas in the given database instance are listed.
7. Select the schema you require and in the Selected Repository – Schema OLL_MDS section, enter ‘Repository Name’ (adf) and the password.
8. Click OK. The following window is displayed.

   

9. Click Repository name ‘mds-adf’ on left panel. You can even select it from right panel.

   

10. Click Add and target to AdminSever and OFSLL_ManagedServer as on right panel.

3.4 Creating Data Source

1. Login to WebLogic Server 12c console (http://hostname:port/console).

   

2. The following window is displayed.

   

3. Click Domain Name > Services > Data Sources.
4. The following window is displayed.

   

5. Click ‘Lock & Edit’ button on the left panel. Click ‘New’ on right panel and select Generic Data Source.

   

6. Enter Data source ‘Name’, JNDI Name as ‘jdbc/ofsllDBConnDS’ and select ‘Oracle’ as Database Type.
7. Click ‘Next’. The following window is displayed.

   

8. Select the Database Driver ‘Oracle's Driver(Thin) for Instance connections; Versions:Any’ as shown above.
9. Click ‘Next’. The following window is displayed.

   

10. Click ‘Next’. The following window is displayed.

    

11. Enter Database details click ‘Next’. The following window is displayed.

    

12. Click ‘Test Configuration’. The following window is displayed.

    

13. Displays confirmation message as ‘Connection test succeeded’. Click ‘Next’. The following window is displayed.

    

14. Select target Servers ‘AdminServer’ and ‘OFSLL_ManagedServer’ and click ‘Finish’. The following window is displayed.

    

15. Click ‘Activate Changes’ on the left panel.

Update the following parameters in JDBC data source connection pool:

1. Select Services > Data Sources > select the OFSLL data source > Connection Pool.
2. Initial capacity and Maximum capacity is defaulted to 15, if the number of concurrent users are more this needs to be increased.
3. Click Advanced button and update the following:

• Inactive Connection Timeout=900
• Uncheck the ‘Wrap Data Types’ parameter for better performance.

4. Click ‘Save’.

Note

User Authentication and Management is outside of Oracle Financial Services Lending and Leasing application. Organizations can use an LDAP implementation for authentication. For Development and Testing purpose, the following sections can be configured for au­thentication:

3.5 Creating SQL Authentication Provider

3.6 Creating User Groups and Users

3.7 Implementing JMX Policy for Change Password

4.1 Configuring Password Policy for SQL Authenticator

4.2 Configuring User Lockout Policy

 

3.5 Creating SQL Authentication Provider

1. Login to WebLogic server administration console and click ‘Security Realms’ in left panel. The following window is displayed.

   

2. Click ‘myrealm’ on right panel. The following window is displayed.

   

3. Click on Providers tab. The following window is displayed.

   

4. Click ‘Lock & Edit’ to unlock the screen and click ‘New’ button in Authentication Providers sub tab. The following window is displayed.

   

5. Create Authentication provider with following values:

• Name: OFSLLDBAuthenticator
• Type: SQLAuthenticator

6. Click ‘OK’. The following window is displayed.

   

7. Click on ‘Activate Changes’. The following window is displayed.

   

Authentication order should be maintained as mentioned in the above screen. ‘OFSLLDBAuthenticator’ will be displayed as above.

8. Click on ‘OFSLLDBAuthenticator’. The following window is displayed.

   

9. Select ‘SUFFICIENT’ as the Control Flag and click Save.
10. Click Provider Specific sub tab under Configuration tab. The following window is displayed.

    

11. Specify the following values in corresponding fields:

• Data Source Name: OFSLL
• Password Style Retained: Uncheck
• Password Algorithm: SHA-512
• Password Style: SALTEDHASHED
• Provide the SQL Queries from the column Corresponding SQL Queries as per OFSLL Tables as given below.

  Operation	Default SQL Query from Weblogic	Corresponding SQL Queries as per our Tables
  SQL Get Users Password:	SELECT U_PASS­WORD FROM USERS WHERE U_NAME = ?	SELECT UAU_USR_PASSWORD FROM USER_AUTHORISATIONS WHERE UAU_USR_CODE = ?
  SQL Set User Password:	UPDATE USERS SET U_PASSWORD = ? WHERE U_NAME = ?	UPDATE USER_AUTHORISATIONS SET UAU_USR_PASSWORD = ? WHERE UAU_USR_CODE = ?
  SQL User Exists:	SELECT U_NAME FROM USERS WHERE U_NAME = ?	SELECT UAU_USR_CODE FROM USER_AUTHORISATIONS WHERE UAU_USR_CODE = ?
  SQL List Users:	SELECT U_NAME FROM USERS WHERE U_NAME LIKE ?	SELECT UAU_USR_CODE FROM USER_AUTHORISATIONS WHERE UAU_USR_CODE LIKE ?
  SQL Create User:	INSERT INTO USERS VALUES ( ? , ? , ? )	INSERT INTO USER_AUTHORISA­TIONS(UAU_USR_CODE, UAU_USR_­PASSWORD,UAU_DESC) VALUES(?,?,?)
  SQL Remove User:	DELETE FROM USERS WHERE U_NAME = ?	DELETE FROM USER_AUTHORISA­TIONS WHERE UAU_USR_CODE= ?
  SQL List Groups:	SELECT G_NAME FROM GROUPS WHERE G_NAME LIKE ?	SELECT UGR_GROUP_CODE FROM USER_GROUPS WHERE UGR_GROUP_CODE LIKE ?
  SQL Group Exists:	SELECT G_NAME FROM GROUPS WHERE G_NAME = ?	SELECT UGR_GROUP_CODE FROM USER_GROUPS WHERE UGR_GROUP_CODE = ?
  SQL Create Group:	INSERT INTO GROUPS VALUES ( ? , ? )	INSERT INTO USER_GROUPS(UGR_GROUP_CODE,UGR_GROUP_DESC) VALUES(?,?)
  SQL Remove Group:	DELETE FROM GROUPS WHERE G_NAME = ?	DELETE FROM USER_GROUPS WHERE UGR_GROUP_CODE = ?
  SQL Is Mem­ber:	SELECT G_MEMBER FROM GROUPMEM­BERS WHERE G_NAME = ? AND G_MEMBER = ?	SELECT UGM_MEMBER_USR_CODE FROM USER_GROUP_MEMBERS WHERE UGM_MEM­BER_GROUP_CODE= ? AND UGM_MEMBER_USR_CODE = ?
  SQL List Mem­ber Groups:	SELECT G_NAME FROM GROUPMEM­BERS WHERE G_MEMBER = ?	SELECT UGM_MEM­BER_GROUP_CODE FROM USER_GROUP_MEMBERS WHERE UGM_MEMBER_USR_CODE= ?
  SQL List Group Mem­bers:	SELECT G_MEMBER FROM GROUPMEM­BERS WHERE G_NAME = ? AND G_MEMBER LIKE ?	SELECT UGM_MEMBER_USR_CODE FROM USER_GROUP_MEMBERS WHERE UGM_MEM­BER_GROUP_CODE= ? AND UGM_MEMBER_USR_CODE LIKE ?
  SQL Remove Group Mem­berships:	DELETE FROM GROUPMEMBERS WHERE G_MEMBER = ? OR G_NAME = ?	DELETE FROM USER_GROUP_MEM­BERS WHERE UGM_MEMBER_US­R_CODE= ? OR UGM_MEMBER_GROUP_CODE= ?
  SQL Add Member To Group:	INSERT INTO GROUPMEMBERS VALUES( ?, ?)	INSERT INTO USER_GROUP_MEM­BERS (UGM_MEM­BER_GROUP_CODE,UGM_MEMBER_USR_CODE) VALUES(?,?)
  SQL Remove Member From Group:	DELETE FROM GROUPMEMBERS WHERE G_NAME = ? AND G_MEMBER = ?	DELETE FROM USER_GROUP_MEM­BERS WHERE UGM_MEM­BER_GROUP_CODE= ? AND UGM_MEMBER_USR_CODE= ?
  SQL Remove Group Mem­ber:	DELETE FROM GROUPMEMBERS WHERE G_NAME = ?	DELETE FROM USER_GROUP_MEM­BERS WHERE UGM_MEM­BER_GROUP_CODE= ?
  SQL Get User Description:	SELECT U_DESCRIP­TION FROM USERS WHERE U_NAME = ?	SELECT UAU_DESC FROM USER_AU­THORISATIONS WHERE UAU_US­R_CODE = ?
  SQLSet User Description:	UPDATE USERS SET U_DESCRIPTION = ? WHERE U_NAME = ?	UPDATE USER_AUTHORISATIONS SET UAU_DESC= ? WHERE UAU_US­R_CODE= ?
  SQL Get Group Descrip­tion:	SELECT G_DE­SCRIPTION FROM GROUPS WHERE G_NAME = ?	SELECT UGR_GROUP_DESC FROM USER_GROUPS WHERE UGR_GROUP_CODE= ?
  SQL Set Group Description:	UPDATE GROUPS SET G_DESCRIP­TION = ? WHERE G_NAME = ?	UPDATE USER_GROUPS SET UGR_GROUP_DESC= ? WHERE UGR_GROUP_CODE= ?
  Provider Name	OFSLLDBAuthentica­tor

 

12. Click ‘Save’.

Note

Application server needs to be restarted for these changes to take effect.

3.6 Creating User Groups and Users

3.6.1 Creating Users

Create an OFSLL application super user to login to the application.

A script is provided in the distribution media in the dba_utils folder to create an user.

Note

By default there are no users created to login to OFSLL application.

Login as application schema owner and run the script ‘crt_app_user.sql script’ to create OFSLL application user.

1. Login into WebLogic server console.
2. Click ‘Security Realms’ on the left panel.
3. Click ‘myrealm’ on the right panel..

   

4. Select ‘Users’ tab under Users and Groups.
5. If SQLAuthenticator is configured as a Security Provider for the OFSLL application, the Users are automatically created in weblogic when created through an application.

   

3.6.2 Creating User Groups

1. Select ‘Groups’ tab under Users and Groups.
2. If SQLAuthenticator is configured as a Security Provider for the OFSLL application, the Groups are automatically created in weblogic when created through an application.

   

3.6.3 Assigning Users to Groups

The USERS are automatically mapped to default application group - OFSLL_USER.

3.6.4 Resetting password via weblogic console

1. Click on ‘User’. Select Passwords tab and enter new password and confirm password.

   

2. Click ‘Save’.The following window displayed.

   

3.7 Implementing JMX Policy for Change Password

1. Login to Oracle WebLogic Server 12c console (http://hostname:port/console)

Note

The Change Password feature uses the JMX Policy configured on the domain. Hence, the AdminServer is required to be up and running to enable this.

2. Click Domain > Security > myrealm > Configuration

   

3. To enable JMX policy select the ‘Use Authorization Providers to Protect JMX Access’ check box on the right panel

   

4. Click ‘Save’ and restart the server.
5. Re-login to console.
6. Click Domain > Security > myrealm > Roles and Policies > Realm Policies

Note

If server is not restarted, JMX Policy Editor option will not appear

7. Click on JMX Policy Editor to configure

   

8. Select ‘GLOBAL SCOPE’ and click Next.

   

9. Select weblogic.security.providers.authentication.
10. Select ‘SQLAuthenticatorMBean’. Click ‘Next’.

    

11. Expand ‘Operations: Permissions to Invoke’ and select ‘ChangeUserPassword’.
12. Click ‘Create Policy’. The following window is displayed for Authorization providers where you can add conditions to setup the policy.
13. Click ‘Add Condition’. The below screen will be displayed.

    

14. For Predicate List, select Group for configuration. Click ‘Next’.

    

15. Select user roles for application.
16. Click Finish. Click on Save to complete the configuration. The following window will be displayed.